|
|
|
|
|
|
|
Abnormal Path: The Account Number on the Deposit Is Wrong. |
|
|
|
| | 1. The Bank Teller requests that the Samsona Bank Teller System store the deposit transaction persistently. | | 2. The Samsona Bank Teller System validates the deposit information and finds the account number is wrong. | | 3. The Samsona Bank Teller System notifies the Bank Teller of the error. |
|
|
|
|
|
Here, the scenario has been simplified to the interaction between the Bank Teller and the Samsona Bank Teller System. With more advanced scripts, you can include the actual names of forms and objects participating in the scenario. This scenario script, and the sequence diagrams, can be migrated to test scripts as follows: |
|
|
|
|
|
|
|
|
Test Script #1: Deposit Funds into Basic Personal Checking AccountNormal |
|
|
|
| | 1. A Bank Teller requests a given customer's basic personal checking account from the Samsona Bank Teller System by entering the customer's appropriate account number. | | 2. When the account is presented to the Bank Teller, the Bank Teller enters the deposit amount. | | 3. The Bank Teller requests that the Samsona Bank Teller System store the deposit transaction persistently. |
|
|
|
|
|
Test Script #2: The Account Number on the Deposit Is Wrong. |
|
|
|
| | 1. The Bank Teller requests that the Samsona Bank Teller System store the deposit transaction persistently. | | 2. The Samsona Bank Teller System validates the deposit information and finds the account number is wrong. | | 3. The Samsona Bank Teller System notifies the Bank Teller of the error. |
|
|
|
|
|
Note
As mentioned earlier, use cases provide the basis for test cases, and in fact, both are equivalent. Use cases, then, make test planning much easier for the test team, which is especially important for components. Given that many testers are not expert at the relatively new ActiveX component technology, use cases for component systems help take much (if not all) of the guesswork out of formulating test cases. |
|
|
|
|
|
|